Method and apparatus for maintaining active calls during failover of network elements

ABSTRACT

A method and apparatus for keeping transitory state in a packet network so that in the event of a failover of a network element, existing active calls can be quickly re-established by the packet network or briefly held in a suspended state until the affected network element returns to a healthy state is disclosed.

The present invention relates generally to communication networks and, more particularly, to a method and apparatus for maintaining active calls during failover of network elements in packet networks, e.g. Voice over Internet Protocol (VoIP) networks.

BACKGROUND OF THE INVENTION

Users of telephony services occasionally experience disruptions to their conversations due to network events such as failovers and other transitory service failures where calls in progress are dropped. These failovers can be due to regular maintenance of network elements or caused by unrecoverable failures in network elements. These events although rare can cause a great deal of frustration to residential users and can seriously impact business users who may lose valuable sales as a result of cut off calls. After such an event, users are forced to hang up, and reconnect to the terminating endpoint thereby costing them both time and money.

Therefore, a need exists for a method and apparatus for maintaining active calls during failover of network elements in a packet network, e.g., a VoIP network.

SUMMARY OF THE INVENTION

In one embodiment, the present invention enables a method for keeping transitory state in a packet network, e.g., a VoIP network. By maintaining the transitory state, if a failover of a network element occurs, existing active calls can be quickly re-established by the packet network or briefly held in a suspended state until the affected network element returns to a healthy state.

BRIEF DESCRIPTION OF THE DRAWINGS

The teaching of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an exemplary Voice over Internet Protocol (VoIP) network related to the present invention;

FIG. 2 illustrates an example of maintaining active calls during failover of network elements in a VoIP network of the present invention;

FIG. 3 illustrates a flowchart of a method for maintaining active calls during failover of one network element to another network element in a VoIP network of the present invention;

FIG. 4 illustrates a flowchart of a method for maintaining active calls during failover of a component within a network element in a VoIP network of the present invention; and

FIG. 5 illustrates a high level block diagram of a general purpose computer suitable for use in performing the functions described herein.

To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.

DETAILED DESCRIPTION

To better understand the present invention, FIG. 1 illustrates an example network, e.g., a packet network such as a VoIP network related to the present invention. Exemplary packet networks include internet protocol (IP) networks, asynchronous transfer mode (ATM) networks, frame-relay networks, and the like. An IP network is broadly defined as a network that uses Internet Protocol to exchange data packets. Thus, a VoIP network or a SoIP (Service over Internet Protocol) network is considered an IP network.

In one embodiment, the VoIP network may comprise various types of customer endpoint devices connected via various types of access networks to a carrier (a service provider) VoIP core infrastructure over an Internet Protocol/Multi-Protocol Label Switching (IP/MPLS) based core backbone network. Broadly defined, a VoIP network is a network that is capable of carrying voice signals as packetized data over an IP network. The present invention is described below in the context of an illustrative VoIP network. Thus, the present invention should not be interpreted to be limited by this particular illustrative architecture.

The customer endpoint devices can be either Time Division Multiplexing (TDM) based or IP based. TDM based customer endpoint devices 122, 123, 134, and 135 typically comprise of TDM phones or Private Branch Exchange (PBX). IP based customer endpoint devices 144 and 145 typically comprise IP phones or PBX. The Terminal Adaptors (TA) 132 and 133 are used to provide necessary interworking functions between TDM customer endpoint devices, such as analog phones, and packet based access network technologies, such as Digital Subscriber Loop (DSL) or Cable broadband access networks. TDM based customer endpoint devices access VoIP services by using either a Public Switched Telephone Network (PSTN) 120, 121 or a broadband access network via a TA 132 or 133. IP based customer endpoint devices access VoIP services by using a Local Area Network (LAN) 140 and 141 with a VoIP gateway or router 142 and 143, respectively.

The access networks can be either TDM or packet based. A TDM PSTN 120 or 121 is used to support TDM customer endpoint devices connected via traditional phone lines. A packet based access network, such as Frame Relay, ATM, Ethernet or IP, is used to support IP based customer endpoint devices via a customer LAN, e.g., 140 with a VoIP gateway and router 142. A packet based access network 130 or 131, such as DSL or Cable, when used together with a TA 132 or 133, is used to support TDM based customer endpoint devices.

The core VoIP infrastructure comprises of several key VoIP components, such the Border Element (BE) 112 and 113, the Call Control Element (CCE) 111, and VoIP related servers 114. The BE resides at the edge of the VoIP core infrastructure and interfaces with customers endpoints over various types of access networks. A BE is typically implemented as a Media Gateway and performs signaling, media control, security, and call admission control and related functions. The CCE resides within the VoIP infrastructure and is connected to the BEs using the Session Initiation Protocol (SIP) over the underlying IP/MPLS based core backbone network 110. The CCE is typically implemented as a Media Gateway Controller and performs network wide call control related functions as well as interacts with the appropriate VoIP service related servers when necessary. The CCE functions as a SIP back-to-back user agent and is a signaling endpoint for all call legs between all BEs and the CCE. The CCE may need to interact with various VoIP related servers in order to complete a call that require certain service specific features, e.g. translation of an E.164 voice network address into an IP address.

For calls that originate or terminate in a different carrier, they can be handled through the PSTN 120 and 121 or the Partner IP Carrier 160 interconnections. For originating or terminating TDM calls, they can be handled via existing PSTN interconnections to the other carrier. For originating or terminating VoIP calls, they can be handled via the Partner IP carrier interface 160 to the other carrier.

In order to illustrate how the different components operate to support a VoIP call, the following call scenario is used to illustrate how a VoIP call is setup between two customer endpoints. A customer using IP device 144 at location A places a call to another customer at location Z using TDM device 135. During the call setup, a setup signaling message is sent from IP device 144, through the LAN 140, the VoIP Gateway/Router 142, and the associated packet based access network, to BE 112. BE 112 will then send a setup signaling message, such as a SIP-INVITE message if SIP is used, to CCE 111. CCE 111 looks at the called party information and queries the necessary VoIP service related server 114 to obtain the information to complete this call. If BE 113 needs to be involved in completing the call; CCE 111 sends another call setup message, such as a SIP-INVITE message if SIP is used, to BE 113. Upon receiving the call setup message, BE 113 forwards the call setup message, via broadband network 131, to TA 133. TA 133 then identifies the appropriate TDM device 135 and rings that device. Once the call is accepted at location Z by the called party, a call acknowledgement signaling message, such as a SIP-ACK message if SIP is used, is sent in the reverse direction back to the CCE 111. After the CCE 111 receives the call acknowledgement message, it will then send a call acknowledgement signaling message, such as a SIP-ACK message if SIP is used, toward the calling party. In addition, the CCE 111 also provides the necessary information of the call to both BE 112 and BE 113 so that the call data exchange can proceed directly between BE 112 and BE 113. The call signaling path 150 and the call data path 151 are illustratively shown in FIG. 1. Note that the call signaling path and the call data path are different because once a call has been setup up between two endpoints, the CCE 111 does not need to be in the data path for actual direct data exchange.

Note that a customer in location A using any endpoint device type with its associated access network type can communicate with another customer in location Z using any endpoint device type with its associated network type as well. For instance, a customer at location A using IP customer endpoint device 144 with packet based access network 140 can call another customer at location Z using TDM endpoint device 123 with PSTN access network 121. The BEs 112 and 113 are responsible for the necessary signaling protocol translation, e.g., SS7 to and from SIP, and media format conversion, such as TDM voice format to and from IP based packet voice format.

Users of telephony services occasionally experience disruptions to their conversations due to network events such as failovers and other transitory service failures where calls in progress are dropped. These failovers can be due to regular maintenance of network elements or caused by unrecoverable failures in network elements. These events although rare can cause a great deal of frustration to residential users and can seriously impact business users who may lose valuable sales as a result of cut off calls. After such an event, users are forced to hang up, and reconnect to the terminating endpoint, thereby costing them both time and money.

To address this criticality, the present invention enables a method for keeping transitory state in the packet network so that in the event of a failover of a network element, existing active calls can be quickly re-established by the network or briefly held in a suspended state until the affected network element returns to a healthy state.

FIG. 2 illustrates an example of maintaining active calls during failover of network elements in a packet network, e.g., a VoIP network. In FIG. 2, endpoint 231 and endpoint 232 are engaged in an ongoing call conversation using media path 241 traversing thru BE 212 and BE 213. In one embodiment of the present invention, when a failover of a component within BE 213 occurs, whether it is due to network maintenance or network equipment component failure, BE 213 will keep the existing call in a suspended state when it is performing failover operations within the system until it is returned to a healthy state. While the failover operation is being performed, BE 213 keeps all the active call states within the system to ensure active calls are not lost during the failover attempt.

In another embodiment of the present invention, when a failover from BE 213 to standby BE 214 occurs, whether it is due to network maintenance or network equipment component failure, BE 213 will keep the existing call in a suspended state and then transfer all the active call states currently running in BE 213 to standby BE 214 using flow 242. After the active call states have been transferred to BE 214, BE 214 will switch from the standby mode to the active mode and take over all active calls that have been placed in suspended state originally supported by BE 213. The media path 241 will be switched to media path 243 when BE 214 becomes active to take over calls originally supported by BE 213.

Note that the described failover scenarios are applicable to, but are not limited to, other network element types as well, such as Media Server (MS), CCE, or even Application Server (AS). A CCE is a network element that performs call control functions to setup a call, an AS is a network element that comprises the data as well as applications that the CCE needs in order to setup a call, and a Media Server (MS) is a special server that typically handles and terminates media streams, and to provide services such as announcements, bridges, transcoding, and Interactive Voice Response (IVR) messages.

FIG. 3 illustrates a flowchart of a method 300 for maintaining active calls during failover of one network element to another network element in a packet network, e.g., a VoIP network. Method 300 starts in step 305 and proceeds to step 310.

In step 310, the method 300 initiates a failover of an active network element to a standby network element. The failover can be triggered by either a maintenance event or a network element failure event. In step 320, the method keeps all active calls in suspended state within the active system. In step 330, the method transfers call states of all active calls currently in suspended state in the active network element to a standby network element. In step 340, the method switches over active calls to the standby network element by activating the transferred call states of all suspended active calls in the standby network element. The standby network element is now in an active mode and no longer in the standby mode. In step 350, the method changes all active calls that have been placed in suspended state to active state again. The method ends in step 360.

FIG. 4 illustrates a flowchart of a method 400 for maintaining active calls during failover of a component within a network element in a packet network, e.g., a VoIP network. Method 400 starts in step 405 and proceeds to step 410.

In step 410, the method 400 initiates a failover of an active component to a standby component within a network element. The failover can be triggered by either a maintenance event or a network element failure event. In step 420, the method keeps all active calls in suspended state within the network element. In step 430, the method transfer call states of all active calls currently in the active component, which is failing over, to the standby component within the network element. In step 440, the method switches over active calls to the standby component within the network element. The standby component within the network element is now in an active mode and no longer in the standby mode. In step 450, the method changes all active calls that have been placed in suspended state to active state again. The method ends in step 460.

It should be noted that if the failover operations fail to complete within a pre-specified period of time, all active calls will be dropped and need to be redialed.

FIG. 5 depicts a high level block diagram of a general purpose computer suitable for use in performing the functions described herein. As depicted in FIG. 5, the system 500 comprises a processor element 502 (e.g., a CPU), a memory 504, e.g., random access memory (RAM) and/or read only memory (ROM), an active calls maintenance module 505, and various input/output devices 506 (e.g., storage devices, including but not limited to, a tape drive, a floppy drive, a hard disk drive or a compact disk drive, a receiver, a transmitter, a speaker, a display, a speech synthesizer, an output port, and a user input device (such as a keyboard, a keypad, a mouse, and the like)).

It should be noted that the present invention can be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a general purpose computer or any other hardware equivalents. In one embodiment, the present active calls maintenance module or process 505 can be loaded into memory 504 and executed by processor 502 to implement the functions as discussed above. As such, the present active calls maintenance process 505 (including associated data structures) of the present invention can be stored on a computer readable medium or carrier, e.g., RAM memory, magnetic or optical drive or diskette and the like.

While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. 

1. A method for maintaining active calls during failover in a communication network, comprising: transferring call states of the active calls in an active network element to a standby network element if said failover relates to said active network element; transferring call states of the active calls in an active component of said active network element to a standby component within said active network element if said failover relates to said active component of said network element; and switching over the active calls to said standby network element or said standby component within said active network element by activating said transferred call states of said active calls.
 2. The method of claim 1, wherein said communication network is a Voice over Internet Protocol (VoIP) network or a Service over Internet Protocol (SoIP) network.
 3. The method of claim 1, wherein said transferring comprises: keeping said active calls in a suspended active state.
 4. The method of claim 1, wherein said call states transferring is initiated by a network maintenance event, an active network element failure event, or an active component within an active network element failure event.
 5. The method of claim 1, wherein said activating comprises: modifying said active calls from suspended active states to active states.
 6. The method of claim 1, wherein said switching over active calls to said standby network element comprises: modifying a current media path of said actives calls to a new media path to pass through said standby network element.
 7. The method of claim 1, wherein if said transferring and switching fail to complete within a pre-specified period of time, said active calls are dropped.
 8. A computer-readable medium having stored thereon a plurality of instructions, the plurality of instructions including instructions which, when executed by a processor, cause the processor to perform the steps of a method for maintaining active calls during failover in a communication network, comprising: transferring call states of the active calls in an active network element to a standby network element if said failover relates to said active network element; transferring call states of the active calls in an active component of said active network element to a standby component within said active network element if said failover relates to said active component of said network element; and switching over the active calls to said standby network element or said standby component within said active network element by activating said transferred call states of said active calls.
 9. The computer-readable medium of claim 8, wherein said communication network is a Voice over Internet Protocol (VoIP) network or a Service over Internet Protocol (SoIP) network.
 10. The computer-readable medium of claim 8, wherein said transferring comprises: keeping said active calls in a suspended active state.
 11. The computer-readable medium of claim 8, wherein said call states transferring is initiated by a network maintenance event, an active network element failure event, or an active component within an active network element failure event.
 12. The computer-readable medium of claim 8, wherein said activating comprises: modifying said active calls from suspended active states to active states.
 13. The computer-readable medium of claim 8, wherein said switching over active calls to said standby network element comprises: modifying a current media path of said actives calls to a new media path to pass through said standby network element.
 14. The computer-readable medium of claim 8, wherein if said transferring and switching fail to complete within a pre-specified period of time, said active calls are dropped.
 15. An apparatus for maintaining active calls during failover in a communication network, comprising: means for transferring call states of the active calls in an active network element to a standby network element if said failover relates to said active network element; means for transferring call states of the active calls in an active component of said active network element to a standby component within said active network element if said failover relates to said active component of said network element; and means for switching over the active calls to said standby network element or said standby component within said active network element by activating said transferred call states of said active calls.
 16. The apparatus of claim 15, wherein said communication network is a Voice over Internet Protocol (VoIP) network or a Service over Internet Protocol (SoIP) network.
 17. The apparatus of claim 15, wherein each of said transferring means keeps said active calls in a suspended active state.
 18. The apparatus of claim 15, wherein said call states transfer is initiated by a network maintenance event, an active network element failure event, or an active component within an active network element failure event.
 19. The apparatus of claim 15, wherein said activating comprises: modifying said active calls from suspended active states to active states.
 20. The apparatus of claim 15, wherein said switching means modifies a current media path of said actives calls to a new media path to pass through said standby network element. 